-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AC-2498-Images lacking meaningful alternative text. (Account - Order … #3944
Conversation
|
@magento create issue from PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @glo82145 - Would you take a look and resolve the failing unit test please? useCustomerWishlistSkus.spec.js
run cypress |
Successfully started codebuild job for |
LogERROR ON TASK: cypressTests
|
QA Approved |
…History)
Description
Reproduction Steps
Sign In > select "Order History" from account dropdown - [NODE][body>div:nth-of-type(1)>:nth-child(1)>:nth-child(3)]
Actual Behavior
In the Order History list, when an order accordion is closed, the product images do not provide meaningful alternative text - each image listed has alt text of "Main". The information conveyed by these images - i.e. a quick view of products included in the order - is not provided to screen reader users.
Note that there are two elements for each product image (for eager and lazy loading); although the eager image is visually hidden, it is still available to assistive technology. As a result, the same alt text for each product is announced twice.
Expected Behavior
Images that convey information must provide descriptive textual alternatives. In this case, the alt text for each image should be brief but identifying image about the product, likely the product name.
Ensure that content intended to be hidden from all users, such as the eager image once the lazy image loads, is also hidden from assistive technology.
Related Issue
Closes #AC-2498.
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist
Resolved issues: